Java classes must declare any checked exceptions they throw in the method signature , and any method that calls a method that throws a checked exception of type e must either catch e or must also be declared to throw e or a superclass of e Java类必须在方法签名中声明它们所抛出的任何检查型异常，并且对于任何方法，如果它调用的方法抛出一个类型为e的检查型异常，那么它必须捕获e或者也声明为抛出e （或者e的一个父类） 。
Eckel advocates making all exceptions unchecked , and offers the class in listing 2 as a means for turning checked exceptions into unchecked ones while preserving the ability to catch specific types of exceptions as they are propagated up the stack see his article in the resources section for an explanation of how it can be used Eckel提倡将所有的异常都作为非检查型的，并且提供清单2中的类作为将检查型异常转变为非检查型异常的一个方法，同时保留当异常从栈向上扩散时捕获特定类型的异常的能力（关于如何使用该方法的解释，请参阅他在
Recently , several well - regarded experts , including bruce eckel and rod johnson , have publicly stated that while they initially agreed completely with the orthodox position on checked exceptions , they ve concluded that exclusive use of checked exceptions is not as good an idea as it appeared at first , and that checked exceptions have become a significant source of problems for many large projects 最近，几位受尊敬的专家，包括bruce eckel和rod johnson ，已经公开声明尽管他们最初完全同意检查型异常的正统观点，但是他们已经认定排他性使用检查型异常的想法并没有最初看起来那样好，并且对于许多大型项目，检查型异常已经成为一个重要的问题来源。
Both eckel and johnson point to a similar list of problems with checked exceptions ; some are inherent properties of checked exceptions , some are properties of the particular implementation of checked exceptions in the java language , and some are simply observations about how the widespread misuse of checked exceptions has become such a significant problem that perhaps the mechanism needs to be rethought Eckel和johnson都指出了一个关于检查型异常的相似的问题清单；一些是检查型异常的内在属性，一些是检查型异常在java语言中的特定实现的属性，还有一些只是简单的观察，主要是关于检查型异常的广泛的错误使用是如何变为一个严重的问题，从而导致该机制可能需要被重新考虑。
Checked exceptions represent useful information about the operation of a legally specified request that the caller may have had no control over and that the caller needs to be informed about - for example , the file system is now full , or the remote end has closed the connection , or the access privileges don t allow this action 检查型异常代表关于一个合法指定的请求的操作的有用信息，调用者可能已经对该操作没有控制，并且调用者需要得到有关的通知例如，文件系统已满，或者远端已经关闭连接，或者访问权限不允许该动作。
The documentation issue further underscores why laziness is a bad reason to choose to use unchecked exceptions , because the documentation burden on packages that use unchecked exceptions should be even higher than with checked exceptions as it becomes even more important to document the unchecked exceptions you throw than with checked exceptions 文档化问题进一步强调为什么懒惰是导致选择使用非检查型异常的一个不好的原因，因为对于文档化增加给包的负担，使用非检查型异常应该比使用检查型异常甚至更高（当文档化您所抛出的非检查型异常比检查型异常变得更为重要的时候） 。
